Users with the required User role permissions can deploy an application and make it available within the organization, depending on the application configuration and access settings.

To deploy a Helm Chart app, the general steps are as follows:

1. Select App: Users can browse applications shown on the page, select the Helm chart that needs to be deployed. Each Helm-chart includes detailed application description and configuration options to help users understand application features.
2. Configuration Parameters: During the deployment process, users can configure specific parameters according to application requirements, such as the number of running instances (replica), environment variables, storage volumes, etc. Helm provides flexible configuration options to support personalized customization of applications.
3. Check the Deployment status: After the deployment process is complete, users can check the deployment status of the application in EonKube. This includes Pod's running status, event logs, and resource usage to help users monitor and manage applications.

Procedure

1. Go to EonKube > Apps > Marketplace.
2. Use the filter or search function to locate the application.
3. Click the application block to enter the details page.
4. Review the application information, including the description, prerequisites, and available chart versions.
5. If needed, select a different Chart Version.
6. Click Install.
7. In Install: Step 1 configure the application Metadata:
   • Namespace: Select the namespace for this application to install.
   • Name: Specify a unique name for this application in lowercase.
   • (Optional) Customize Helm options before install: If needed, you can click this option to configure additional deployment options for this app in step 3.
8. Click Next.
9. In Install: Step 2, configure the application values as required.
   • General: Check the default settings of APP replicas, CPU and Memory and adjust if needed.
   • Image: Select Use Harbor Image Repository by clicking on it if available.
   • Storage: Check if use the default settings of StorageClass and storage size for your app retained data.
   • Service:
     • App Service Name: Specify an identifying name.
     • App Image Service Type: Select LoadBalancer, NodePort, or ClusterIP. Service options vary by application.
       • LoadBalancer: Configure a load balancer IP from the VIP (Virtual IP) address pool. This IP will be used to route external traffic to the application.
         – When selecting LoadBalancer, specify Static Virtual IP. If needed, select to Enable Virtual IP Sharing
         * When enabling virtual IP Sharing, this means that multiple apps will share the same IP address, while the connections will be assigned through different ports. You can change the port number by editing the YAML file of this app.
       • NodePort: Configure a specific port number. If no port is configured, a random port will be assigned automatically.
       • ClusterIP: Configure the ingress setting to expose MySQL to the Internet.
       • Show advanced service settings, you can enable and specify a domain name, and enable Ingress settings for MySQL and specify the connection URL.
   • APP setting: Check the environment keys and environment values.
   • Scheduling: Setting node affinity and spread replicas for APP
     • Schedule: Choose one specific node or multiple nodes for this APP to run:
       • Run POD on any available node: Kubernetes automatically deploys the APP to any available node.
       • Run POD on specific node: select a specific Node to run the APP.
       • Run POD on node(s) matching scheduling rules: Set customized deployment rules filter one or more nodes, including required rules and preferred rules.
     • Spread replicas Define which nodes are eligible to host it and how multiple copies (replicas) should be spread across the physical hardware to ensure high availability.
       • Soft (Default): The system tries to put replicas on different nodes but will put them together if space is tight.
       • Hard: The system must put replicas on different nodes. If you have 3 replicas but only 2 nodes, the 3rd replica will not start.
10. Go to Install: Step 3: If you click Customize Helm options before install in Install: Step 1, you will have 3 steps in procedure. If you did not click it, skip this step in the procedure.
    Check the Supply Additional Deployment Options in Step 3. If needed, click one or more options to enable them:
    • Apply custom resource definitions: The custom resources defined by the Helm chart will be applied during the installation.
    • Execute chart hooks: Run pre-install, post-install, and other Helm chart hooks as defined by the chart.
    • Validate OpenAPI schema: Validate the chart's OpenAPI schema before deployment.
    • Wait: Helm will wait until the deployment is complete and resources are successfully created. The default timeout value is 3600 seconds.
11. Click Install.

For more information about deploying a Helm chart app, see the APP Installation Examples.